-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wip] URL drilldown #68235
[wip] URL drilldown #68235
Conversation
x-pack/plugins/advanced_ui_actions/public/drilldowns/url_drilldown/url_drilldown_definition.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/ui_actions_enhanced/public/actions/action_enhanced.ts
Outdated
Show resolved
Hide resolved
@@ -0,0 +1,104 @@ | |||
/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would split the action license support into its own dedicated PR. To ensure the new APIs are used (and tested), you could modify one of the examples, or add a new one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stacey-gammon, oh, forgot to remove reviewers from this pr. this is a cleaned up version of just license support: #68507
7b69269
to
644fc50
Compare
I will put it on our list to create a description list UI for that variable popover |
const filtersFromEvent = await (async () => { | ||
try { | ||
if (isRangeSelectTriggerContext(context)) | ||
return await createFiltersFromRangeSelectAction(context.data); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as mentioned in the doc, i would prefer if we would not postprocess context.data and expose it directly. it will give more power to the user and it will be easier to extend url drilldown with future triggers.
…down # Conflicts: # x-pack/plugins/ui_actions_enhanced/public/drilldowns/index.ts
💚 Build SucceededBuild metrics@kbn/optimizer bundle module count
History
To update your PR or re-run it, just comment with: |
Summary
URL Drilldown
issue
spec
Reusability considerations:
This is not actually
Url Drilldown
, butSomeEmbeddablesToUrlDrilldown
, as it relies onembeddable
in drilldown context and on support ofValueClickTrigger
&RangeSelectTrigger
. This where url drilldown gets variables from from a tempate. More details here: specThis
EmbeddableToUrlDrilldown
is registered inembeddable_enhanced
plugin. But reusable building block to build other url Drilldowns are inuiActions_enhanced
. How to use them showcased inSampleUrlDrilldown
example.